home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
wildfire.zip
/
TIPS.DOC
< prev
next >
Wrap
Text File
|
1988-10-29
|
4KB
|
87 lines
Hello WildFire Users!
** RELEASE NOTES **
Here are some tricks I've learned that will help you implement doors on
your system.
1. RBBS-PC doors that use DOORINFO1.DEF will NOT look down any path to find
the .DEF file. In your script you must first copy the DOORINFO1.DEF
file from your SF directory to the directory where the RBBS door is at
before changing over there and running the door.
2. PCBoard doors can presently appear in three different flavors.
Doors for PCBoard V 14.x are NOT supported at this time.
Doors for PCBoard V 11.x will run just fine unmodified in any way.
Doors for PCBoard V 12.x REQUIRE the presence of a file called
PCBOARD.DAT in your SF directory. This file is NOT built by WF
because it is a static file and is only created once and then left
alone. It holds the comport number the system is running on and
12.x doors open it to find the port. If you don't have a PCBOARD.DAT
un-pack the one that came with the Wildfire package, follow the short
doc file and configure it for your system. Then place it in your SF
directory and forget about it.
3. Wildcat doors come in two different flavors now. Doors for Wildcat
version 1.10 and 1.11 can be marked in the ATTRIBUTE screen of the
editor as 'W' type doors. Some newer Wildcat doors are specific to
Wildcat Version 1.12. To run these, mark them as a '2' type door
with the editor. In all cases, unless the door documentation TELLS
you it REQUIRES the 1.12 format, mark it as a W type door, if it won't
run that way, THEN mark it as a 2 type door and try again.
4. The conversion process that WF goes through to build the conversion
files for the different types of doors are this:
Doors marked as a 'P' type door get a file created called PCBOARD.SYS.
this file is created in your SF directory and the door .CFG must look
for it there. REMEMBER, some P type doors will REQUIRE the presence
of that PCBOARD.DAT file in your SF directory or they will error
out on you when you try to run them.
Doors marked as a 'W' or '2' type door get a file created called
CALLINFO.BBS. This file is placed in your SF directory and the door
.CFG must look for it there.
Doors marked as an 'R' type door get a file created called DOORINFO1.DEF
This file is placed in your SF directory and MUST be copied by your
script into the directory where the door is at BEFORE you try to
execute the door. If you happen to be running on COM2 instead of COM1
then you must also rename the file from DOORINFO1.DEF to DOORINFO2.DEF.
This of course can be accomplished during the copy operation from the
SF directory to the target door directory.
Doors marked as a 'G' type door get a file created called DOOR.SYS.
This file is placed in your SF directory and the door must look for
it there.
5. In any door that has a MULTI BOARD interface and you get to choose
which interface you'd like to run, the order of preference is this:
Wildcat = First Choice
PCBoard = Second Choice
RBBS = Third Choice.
Experience has taught me that the Wildcat interface is the most
reliable and easy to use, take it whenever you can.
The PCBoard interface is by far more reliable and easy to deal with
than the RBBS interface. USE PCB when your only choices are PCB or
RBBS.
RBBS, use it only if there is no other choice.
GAP, only 3 or 4 doors presently available and the G type converter
will handle them just fine.
Steve
ONE LAST NOTE!!!!!
In your CONFIGURATION FOR SPITFIRE. Set the maximum daily time limit
to the highest that will EVER be permitted on your system. THEN set the
maximum LOG ON time to the SAME number if you want doors to operate
correctly! Reason is that WF CANNOT tell which session a user is in and
will assign them the door times based on how much log on time they have
left THIS session.